Systems and methods for adaptive data replication

ABSTRACT

Systems and methods are provided for adaptive data replication. A first data object is stored. One or more first network characteristics of a communication network are detected. A first replication mode is triggered (e.g., a single-master replication mode) based on the one or more first network characteristics of the communication network. The single-master replication may be configured to facilitate real-time synchronizations (e.g., for critical updates). One or more second network characteristics of the communication network are detected. A second replication mode (e.g., a multi-master replication mode) is triggered based on the one or more second network characteristics. The second replication may be configured to facilitate a delayed synchronization (e.g., for non-critical updates) of the first data object and the second data object using the second update file.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/116,037, filed Aug. 29, 2018, which is a continuation of U.S. patentapplication Ser. No. 15/664,184, filed Jul. 31, 2017, now U.S. Pat. No.10,068,002, which claims the benefit under 35 U.S.C. § 119(e) of theU.S. Provisional Application Ser. No. 62/489,737, filed Apr. 25, 2017,the contents of which is hereby incorporated by reference in itsentirety.

BACKGROUND Technical Field

This disclosure relates to approaches for data replication and datasynchronization.

Description of Related Art

Under conventional approaches, data synchronization may involvetransmitting data from a first system to a second system over a network.For example, data may be pushed or pulled from the first system toupdate corresponding data on the second system. However, typical datasynchronization schemes do not account for changes in networkperformance characteristics. For example, highly-fault tolerant datasynchronization schemes may fail to take advantage of strong networkconnections and may become a bottleneck in various situations (e.g.,multi-user collaboration), while low-fault tolerant data synchronizationschemes may not function when operated over an unreliable network.

SUMMARY

A claimed solution rooted in computer technology overcomes problemsspecifically arising in the realm of computer technology. In variousimplementations, a computing system is configured to provide methods andsystems that facilitate adaptive data replication and/orsynchronization. For example, different data replications modes may beselected based on network performance characteristics (e.g., latency,bandwidth, throughput, connected or disconnected network status, and thelike. In some embodiments, a first replication mode (e.g., asingle-master replication mode) is selected when a sufficiently strongnetwork connection is available (e.g., latency below a particularthreshold value) and/or predicted to become available, and a secondreplication mode (e.g., a multi-master replication mode) is selectedwhen a sufficiently strong network connection is unavailable (e.g.,latency above a particular threshold value) and/or predicted to becomeunavailable. The first replication mode may be used for real-time datareplication or near real-time data replication (e.g., synchronizationperformed every 5 ms), and the second replication mode may be used fordelayed data replication (e.g., synchronization performed every 4hours). The computing system may adapt to accommodate changing networkcharacteristics, and may switch between different replication modes,and/or perform different replication modes in parallel (or,concurrently).

In some embodiments, the computing system may use multiple replicationmodes concurrently, e.g., instead of, or in addition to, switchingbetween replication modes. For example, a data update may be received(e.g., an update to a shared document), and a priority status (e.g.,critical or non-critical) may be determined for the data update and/orportions of the data update. Critical data updates may be replicatedusing a first replication mode, and non-critical data updates may bereplicated using a second replication mode. In some embodiments,critical data updates may be replicated using both the first replicationmode and the second replication mode.

Various embodiments of the present disclosure include systems, methods,and non-transitory computer readable media configured to store a firstdata object, the first data object being associated with a correspondingsecond data object stored by a remote master replication system. One ormore first network characteristics of a communication network aredetected. A first replication mode is triggered based on the one or morefirst network characteristics of the communication network. The firstreplication mode includes receiving a first update of the first dataobject, generating a first update file in response to receiving thefirst update of the first data object, the first update file indicatingthe first update of the first data object, and providing the firstupdate file to the remote master replication system over thecommunication network, the remote master replication system beingconfigured to facilitate a real-time synchronization of the first dataobject and the second data object using the first update file. One ormore second network characteristics of the communication network aredetected. A second replication mode is triggered based on the one ormore second network characteristics. The second replication modeincludes receiving a second update of the first data object, generatinga second update file, the second update file indicating the secondupdate of the first data object, and providing the second update file toa second replication system, the second replication system facilitatinga delayed synchronization of the first data object and the second dataobject using the second update file.

In some embodiments, the one or more first network characteristicscomprise any of latency, bandwidth, throughput, or network connectionstatus.

In some embodiments, the first replication mode comprises asingle-master replication mode, and the second replication modecomprises a multi-master replication mode.

In some embodiments, the second replication mode further includesgenerating an alert based on any of the one or more second networkcharacteristics, or the second replication mode, and presenting thealert to a user of the system.

In some embodiments, the systems, methods, and non-transitory computerreadable media configured to generate an alert based on any of the oneor more second network characteristics, or the second replication mode,and present the alert to a user of the system.

In some embodiments, the systems, methods, and non-transitory computerreadable media configured to determine a priority status of at least aportion of the first update of the first data object, and the firstreplication mode is triggered based on the priority of status of the atleast a portion of the first update of the first data object.

In some embodiments, the second replication system comprises amulti-master replication system, and the second replication mode furtherincludes providing, by the second replication system, the second updatefile to the remote multi-master replication system, generating, by theremote multi-master replication system, a third update file, the thirdupdate file indicating the second update of the first data object,providing, by the remote multi-master replication system, the thirdupdate file to the remote master replication system, and updating, bythe remote master system, the second data object using the third updatefile.

In some embodiments, the second replication mode further includesobtaining, by the second replication system, one or more third dataobjects, the one or more third data objects being associated withcorresponding one or more fourth data objects stored by a remotemulti-master replication system, the second update file furtherindicating the one or more third data objects, and synchronizing, by theremote multi-master replication system, the one or more third dataobjects and the one or more fourth data objects using the second updatefile. In some embodiments, the third and fourth data objects compriseimmutable data objects and the first and second data objects comprisesmutable data objects.

In some embodiments, the third and fourth data objects represent ageographic map, and the first and second data objects represent a pointof interest of the geographic map.

These and other features of the systems, methods, and non-transitorycomputer readable media disclosed herein, as well as the methods ofoperation and functions of the related elements of structure and thecombination of parts and economies of manufacture, will become moreapparent upon consideration of the following description and theappended claims with reference to the accompanying drawings, all ofwhich form a part of this specification, wherein like reference numeralsdesignate corresponding parts in the various figures. It is to beexpressly understood, however, that the drawings are for purposes ofillustration and description only and are not intended as a definitionof the limits of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

Certain features of various embodiments of the present technology areset forth with particularity in the appended claims. A betterunderstanding of the features and advantages of the technology will beobtained by reference to the following detailed description that setsforth illustrative embodiments, in which the principles of thetechnology are utilized, and the accompanying drawings of which:

FIG. 1 depicts a diagram of an example of a system for adaptive datareplication according to some embodiments.

FIG. 2 depicts a diagram of an example of a first replication system(e.g., a single-master replication system) according to someembodiments.

FIG. 3 depicts a diagram of an example of a second replication system(e.g., a multi-master replication system) according to some embodiments.

FIG. 4 depicts a flowchart of an example of a method for adaptive datareplication according to some embodiments.

FIG. 5 depicts a flowchart of an example of a method for performing afirst replication mode (e.g., a single-master replication mode)according to some embodiments.

FIG. 6 depicts a flowchart of an example of a method for performing asecond replication mode (e.g., a multi-master replication mode)according to some embodiments.

FIG. 7 depicts a flowchart of an example of a method of operation of afirst replication system for performing adaptive data replicationaccording to some embodiments.

FIG. 8 depicts a block diagram of an example of a computer system uponwhich any of the embodiments described herein may be implemented.

DETAILED DESCRIPTION

Under conventional approaches, data synchronization may involvetransmitting data from a first system to a second system over a network.For example, data may be pushed or pulled from the first system toupdate corresponding data on the second system. However, typical datasynchronization schemes do not account for changes in networkperformance characteristics. For example, highly-fault tolerant datasynchronization schemes may fail to take advantage of strong networkconnections and may become a bottleneck in various situations (e.g.,multi-user collaboration), while low-fault tolerant data synchronizationschemes may not function when operated over an unreliable network.

A claimed solution rooted in computer technology overcomes problemsspecifically arising in the realm of computer technology. In variousimplementations, a computing system is configured to provide methods andsystems that facilitate adaptive data replication and/orsynchronization. For example, different data replications modes may beselected based on network performance characteristics (e.g., latency,bandwidth, throughput, connected or disconnected network status, and thelike. In some embodiments, a first replication mode (e.g., asingle-master replication mode) is selected when a sufficiently strongnetwork connection is available (e.g., latency below a particularthreshold value) and/or predicted to become available, and a secondreplication mode (e.g., a multi-master replication mode) is selectedwhen a sufficiently strong network connection is unavailable (e.g.,latency above a particular threshold value) and/or predicted to becomeunavailable. The first replication mode may be used for real-time datareplication or near real-time data replication (e.g., synchronizationperformed every 5 ms), and the second replication mode may be used fordelayed data replication (e.g., synchronization performed every 4hours). The computing system may adapt to accommodate changing networkcharacteristics, and may switch between different replication modes,and/or perform different replication modes in parallel (or,concurrently).

In some embodiments, the computing system may use multiple replicationmodes concurrently, e.g., instead of, or in addition to, switchingbetween replication modes. For example, a data update may be received(e.g., an update to a shared document), and a priority status (e.g.,critical or non-critical) may be determined for the data update and/orportions of the data update. Critical data updates may be replicatedusing a first replication mode, and non-critical data updates may bereplicated using a second replication mode. In some embodiments,critical data updates may be replicated using both the first replicationmode and the second replication mode.

FIG. 1 depicts a diagram of an example of a system 100 for adaptive datareplication according to some embodiments. The example system 100 shownin FIG. 1 includes first replication systems 102-1 to 102-n(individually, the first replication system 102, collectively, the firstreplication systems 102), second replication systems 104-1 to 104-n(individually, the second replication system 104, collectively, thesecond replication systems 104), and a communication network 106.

The first replication systems 102 may function to share, replicate,and/or synchronize data over one or more communication networks. Invarious embodiments, functionality of the replication systems 102 can beperformed by one or more servers, workstations, desktop computers,laptop computers, mobile devices (e.g., smartphone or tablet computer),and the like. The replication systems 102 may be geographicallydistributed across any number of geographic area, or may be within thesame geographic area (e.g., a particular data center).

In some embodiments, the first replication systems 102 may comprise asingle-master (or, “master-client”) replication system. The firstreplication systems 102 may operate as master replication systems and/orclient replication systems depending on context. In one example, each ofthe first replication systems 102 may be capable of operating as amaster replication system for data it owns (e.g., data it created), andeach of the first replications systems 102 may be capable of operatingas a client replication system for data shared by the client replicationsystem but owned by a different first replication system 102. Whenoperating as a master, a first replication system 102 may be referred toas a master replication system 102. Similarly, when operating as aclient, a first replication system 102 may be referred to as a clientreplication system 102. Additionally, since the first replicationsystems 102 may share data owned by a variety of different firstreplication systems 102, it will be appreciated that a first replicationsystem 102 may operate simultaneously as both a master replicationsystem with respect to some data, and a client replication system withrespect to other data.

In some embodiments, the first replication systems 102 function to storecorresponding data objects 108-1 to 108-n (individually, the data object108, collectively, the data objects 108). In some embodiments, eachobject data object 108 has a designated owner (or, “master”) firstreplication system 102 and may only be modified by the owner. Forexample, the data object 108-1 may be created and/or owned by the firstreplication system 108-1, and the data object 108-n may comprise a copy(e.g., a local copy) of the of the data object 108-1. The firstreplication system 102-n may modify data objects 108-n, and provide themodifications (or, “updates”) to the first replication system 102-1,which can update the master data object 108-1 accordingly.

As used herein, data objects (e.g., data objects 108 and/or 110) maystore data in arrays, tables, an object-oriented framework, orotherwise. Data objects may store media data (e.g., audio, images,photographs, pictures, video, and the like), and/or other types of data.In some embodiments, data objects may store data representing geographicmaps, and/or points of interest (e.g., landmarks) of geographic maps.For example, points of interest may be stored as an array of identifiersassociated with corresponding landmarks. The data objects may storedata, for example, in one or more tables of a relational database, inone or more arrays, or in an object-oriented framework. However, theembodiments described herein are not limited to relational databases,and any type of datastore may be used, e.g., relational databases,hierarchical databases, and object-oriented databases.

In some embodiments, the first replication systems 102 function toadaptively replicate data objects 108. As used herein, reference to adata object may include the entire data object, or portion thereof(e.g., a modified portion of a data object 108 and/or a modification ofa data object 108). For example, the first replication systems 102 mayreplicate data objects 108 using a replication mode selected based onactual and/or predicted network performance characteristics, and/orbased on a status priority of the data objects 108. Network performancecharacteristics may include latency, bandwidth, throughput, connectionstatus (e.g., connected or disconnected), and the like. Status prioritymay include “critical” or “non-critical”. A critical modification mayinclude removing a point of interest from a map, or other time-sensitivemodification. A non-critical modification may include changing a profilepicture associated with a user making a modification, or othermodification that is not time-sensitive. In one example, a firstreplication system 102 may (i) replicate data using a single-masterreplication mode if a strong network connection is detected and/or ifthe data to be replicated is critical, and/or (ii) provide the data tobe replicated to a second replication system (e.g., second replicationsystem 104 implementing a multi-master replication mode, discussedbelow) if a weak network connection is detected and/or if the data to bereplicated is non-critical.

The second replication systems 104 may function to share, replicate,and/or synchronize data over one or more communication networks. In someembodiments, the second replication systems 104 comprise multi-masterreplication systems, e.g., of the type described in U.S. patentapplication Ser. No. 15/456,256, entitled “Systems and Methods for DataReplication Synchronization,” filed Mar. 10, 2017, and U.S. PatentApplication No. 62/438,190, entitled “Systems and Methods for DataReplication Synchronization,” filed Dec. 22, 2016, both of which areincorporated herein by reference in their entirety. In variousembodiments, functionality of the second replication systems 104 can beperformed by one or more servers, workstations, desktop computers,laptop computers, mobile devices (e.g., smartphone or tablet computer),and the like. The second replication systems 104 may be geographicallydistributed across any number of geographic areas, or may be within thesame geographic area (e.g., a particular data center).

In some embodiments, the second replication systems 104 function toasynchronously propagate changes made to data objects 108 and/or dataobjects 110 to one or more of the other replication second systems 104.For example, in a full-mesh topology, each second replication system 104may be able to propagate changes to any other second replication systems104, although embodiments also support partial-mesh topologies. In anasynchronous replication scheme, each data object 110 may be looselyconsistent with the other data objects 110. For example, the dataobjects 110 may diverge from time to time such that at any given moment,one replication system's view of the body of data associated with thedata objects 110 may be different from another replication system's viewof the body of data. In the absence of new changes, the data objects 110may be expected to eventually become consistent with one another. Insome embodiments, as well as being loosely consistent with one another,the data objects 110 can also be said to be eventually consistent.

In some embodiments, the data objects 110 comprise the same type of dataobject as the data objects 108. In some embodiments, the data objects110 may include one or more immutable components. For example, animmutable component may comprise one or more content items (e.g., afile, binary, and the like) that may not be modified. Accordingly, thesecond replication systems 104 may effectively modify a component (e.g.,a PDF document) by adding a new immutable component (e.g., a secondversion of the PDF document), and/or removing an existing immutablecomponent.

In some embodiments, the second replication systems 104 function toperform delayed replication and/or synchronization. For example, thesecond replication systems 104 may function to replicate data atpredetermined intervals, e.g., as opposed to in real-time or nearreal-time. The predetermined intervals may be based on networkcharacteristics, and/or other factors. The second replications systems104 may utilize a multi-master replication mode, which may be beneficialwhen real-time or near real-time (or, collective, “real-time”)replications are unnecessary and/or when a strong network connection isunavailable. In some embodiments, the second replication systems 104 mayreceive data from one or more remote systems (e.g., first replicationsystems 102) and provide the data to one or more other remote systems(e.g., a remote second replication system 104). For example, a secondreplication system 104 may generate a replication message (or, updatemessage) based on the received data, and configure the message for ahigh-latency transmission and/or multi-master transmission. In someembodiments, the second replication system 104 may not be optimized toreplicate some types of data (e.g., low-latency, high scale sensorfeeds), and first replication systems 102 may attempt to send referencesto data. In some embodiments, the user interface may display an errorwhen attempting to show or access data without a strong networkconnection.

The communication network 106 may represent one or more computernetworks (e.g., LAN, WAN, or the like) or other transmission mediums.The communication network 106 can provide communication between firstreplication systems 102, the second replication system 104, and/or othersystems. In some embodiments, the communication network 106 comprisesone or more computing devices, routers, cables, buses, and/or othernetwork topologies (e.g., mesh, hub-and-spoke, and the like). In someembodiments, the communication network 104 may be wired and/or wireless.In various embodiments, the communication network 104 may comprise theInternet, one or more wide area networks (WANs) or local area networks(LANs), one or more networks that may be public, private, IP-based,non-IP based, and so forth. Communication networks and transmissionmediums are discussed further herein. In various embodiments, thecommunication network 106 comprises any transitory or non-transitorycomputer readable medium (e.g., CD. DVD, and the like).

In some embodiments, the communication network 106 comprises one or moredifferent communication networks, which may be have the same, similar,and/or different network performance characteristics. For example, afirst communication network 106 may be used for real-time communicationand/or single-master replication between first replication system 102, asecond communication network 106 may be used for communication between afirst replication system 102 and a second replication system 104, and athird communication network 106 may be used for communication betweensecond replication systems 104, and the like.

FIG. 2 depicts a diagram 200 of an example of a first replication system102 (e.g., a single-master replication system) according to someembodiments. In the example of FIG. 2, the first replication system 102includes a network performance detection engine 202, a replicationprioritization engine 204, a master replication engine 206, a clientreplication engine 208, a replication mode selection engine 210, acommunication engine 212, and a first replication system datastore 214.

The network performance detection engine 202 may function to determineone or more network performance characteristics of one or moreassociated communication networks (e.g., communication network 106). Insome embodiments, the network performance detection engine 202determines actual and/or anticipated network performancecharacteristics. For example, the network performance detection engine202 may log historical network performance characteristics, and/orotherwise access historical network performance characteristics, of oneor more communication networks, and use the historical networkperformance characteristics to determine anticipated network performancecharacteristics.

The replication prioritization engine 204 may function to determine areplication priority status and/or replication categorization (or,collectively, “priority status”) of a replication message. A replicationmessage may include an update request to modify a shared data object(e.g., an original data object or a copy of a data object). For example,a replication message may include one or more data objects and/or one ormore associated identifiers. The identifiers may be associated with oneor more points of interest of a geographic map. In some embodiments, thepoints of interest may be stored in a first data object 108 and thegeographic map may be stored in a second data object 110.

In some embodiments, a priority status may include one or morecontext-based priority identifiers associated with a replication messageand/or portions of a replication message. As used herein, functionalityperformed with respect to a replication message may be similarlyperformed for one or more portions of a replication message. Forexample, the replication prioritization engine 204 may parse areplication message, and determine corresponding context-based priorityidentifiers for some or all portions of the replication message. In someembodiments, context may include an activity associated with thereplication message (e.g., multi-user collaboration of a shared dataobject), one or more network performance characteristics of acommunication network associated with the replication message, arelative importance of a replication message (e.g., critical ornon-critical), transmission requirements associated with the replicationmessage (e.g., suggested and/or required threshold network performancecharacteristics needed to perform the replication) and/or the like. Forexample, a replication message for updating a point of interest of ageographic map during a collaborative editing session may be assigned acritical priority status because the relative importance of the updateis high (e.g., because users rely on real-time synchronization of pointsof interest). Similarly, a replication message for updating a profilepicture of a user associated with the replication message may beassigned a non-critical priority status (e.g., because users do not relyon real-time synchronization of changes in profile pictures).

The master replication engine 206 may function to implement features ofa master node of a single-master replication mode. For example, themaster replication engine 206 may generate replication messages,designate owners of data objects 108, and create, read, update, delete,and/or otherwise access data objects 108. In some embodiments, themaster replication engine 206 receives and processes replicationmessages to facilitate real-time and/or delayed synchronization of dataobjects 108. Real-time synchronization may include synchronizations thatare processed, or expected to be processed, within a threshold amount oftime and/or frequency. For example, real-time synchronizations mayprovide, receive, and/or exchange synchronization data (e.g.,replication messages) every 5 ms. Delayed synchronizations may includesynchronizations that are processed, or expected to be processed, withinan increased threshold amount of time and/or frequency relative toreal-time synchronizations. For example, delayed synchronizations mayprovide, receive, and/or exchange synchronization data every 4 hours.

In some embodiments, the master replication engine 206 may function toresolve replication conflicts (or, “deconflict” replication conflicts).For example, the master replication engine 206 may receive conflictingreplication messages from multiple client replication systems 102,and/or receive conflicting replication messages provided using differentreplication modes. Conflicts may be resolved manually (e.g., by a user)and/or automatically (e.g., without requiring user input). In oneexample, the master replication engine 206 may receive a firstreplication message to modify a data object 108 provided using asingle-master replication mode, and receive a second replication messageto modify the same data object provided using a multi-master replicationmode. The single-master replication mode may be configured to facilitatereal-time synchronizations, while the multi-master replication mode maybe configured to facilitate delayed synchronizations, which may resultin conflicts. Conflicts may be resolved based on a first-to-arrive basis(e.g., the first replication message received wins and is processed)and/or based on deconfliction rules in replication engine 104. Forexample, some conflicting edits to a data object without multiplicity(e.g., the date of an event) may require manual or automaticdeconfliction. In some embodiments, conflicting edits to a data objectwith multiplicity (e.g., aliases for a person) may be mergedautomatically.

The client replication engine 208 may function to implement features ofa slave node of a single-master replication mode. In some embodiments,the client replication engine 208 functions to generate and providereplication messages to a master replication system 102, and receive andprocess replication messages received from a master replication system102. In some embodiments, the client replication engine 208 performslocal deconflcition of a replication message prior to providing thereplication message to the master replication system. For example, areplication message may include multiple update requests correspondingto the same data object, and conflicts may be resolved on afirst-to-arrive basis at the client replication system 102.

In some embodiments, the client replication engine 208 may generateand/or present (e.g., display) alerts or other notifications based onnetwork performance characteristics of a one or more associatedcommunication networks. For example, if a client replication system 102becomes disconnected from a master replication system 102, or adisconnection is anticipated, the client replication engine 208 maygenerate and/or present an alert indicating the one or more networkperformance characteristics.

In some embodiments, the client replication engine 208 may function togenerate local copies of data objects 108 and/or prevent access to dataobjects 108 (e.g., based on network performance characteristics). Insome embodiments, the master replication engine 206 may prevent accessto data objects 108 instead of, or in addition to, the clientreplication engine 208. In one example, if a client replication system102 becomes disconnected from a master replication system 102, theclient replication engine 208 may create a local copy of the data object108, and modifications may be applied to the local copy. Themodifications may be batched and replicated to the master replicationsystem. For example, the modification may be provided directly to themaster replication system 102 using a single-master replication modewhen a sufficient network connection is available (e.g., based on one ormore network performance characteristic threshold values), and/or themodifications may be provided to a second replication system which canfacilitate replication of the modifications using a multi-masterreplication mode.

The replication mode selection engine 210 may function to select areplication mode for replicating data. In some embodiments, thereplication modes may include a single-master replication mode, amulti-master replication mode, and a parallel (or, “combined”)replication mode. A parallel replication mode may include adaptivelyperforming single-master replication and multi-master replication inparallel. For example, an update request may include portions associatedwith different priority status' (e.g., critical or non-critical). Theportions of the update request flagged as critical may be replicatedusing a single-master replication, and portions of the update requestflagged as non-critical may be replicated using a multi-masterreplication mode. This may help ensure, for example, that performance ofthe single-master replication mode is not unnecessarily eroded bynon-critical updates. In some embodiments, critical updates may beprovided using both a single-master replication mode and a multi-masterreplication mode. This may help improve, for example, the likelihoodthat critical updates are properly received and processed. In someembodiments, the single-master replication mode may comprise ahigher-performance (e.g., low-latency) but lower-fault tolerantreplication mode, while the multi-master replication mode may comprise alower-performance (e.g., high-latency) but higher-fault tolerantreplication mode.

The communication engine 212 may function to send requests, transmitand, receive communications, and/or otherwise provide communication withone or a plurality of systems. In some embodiments, the communicationengine 212 functions to encrypt and decrypt communications. Thecommunication engine 212 may function to send requests to and receivedata from a system through a network or a portion of a network.Depending upon implementation-specific or other considerations, thecommunication engine 212 may send requests and receive data through aconnection, all or a portion of which may be a wireless connection. Thecommunication engine 212 may request and receive messages, and/or othercommunications from associated systems.

The first replication system datastore 214 may function to store, atleast temporarily, data received from one or more other systems. Forexample, the first replication system datastore 214 may store messagesreceived by the communication engine 212, and data objects 108. Likeother datastores described herein, the first replication systemdatastore 214 may reside local to the first replication system 102,and/or comprise a remote storage system (e.g., a cloud storage system).

FIG. 3 depicts a diagram 300 of an example of a second replicationsystem 104 (e.g., a multi-master replication system) according to someembodiments. In the example of FIG. 3, the second replication system 104includes a multi-master replication engine 302, a communication engine304, and a second replication system datastore 306.

The multi-master replication engine 302 may function to implement amulti-master replication mode. For example, the multi-master replicationengine 302 may receive data from remote systems (e.g., first replicationsystems 102) and replicate the data to one or more other remote systems(e.g., second replications systems 104 and/or first replication system102) using a multi-master replication mode. In some embodiments, themulti-master replication engine 302 may obtain data objects 108 andbatch the data objects 108 with one or more previously scheduledreplications of one or more data objects 110.

In some embodiments, the multi-master replication engine 302 functionsto receive, parse, and/or process replication messages. For example, themulti-master replication engine 302 may identify data objects 108 anddata objects 110, process the data objects 110 (e.g., facilitate asynchronization of corresponding data objects 110 using the data objects110 of the replication message), and provide a replication message forthe data objects 108 to an intended target system (e.g., a firstreplication system 102).

The communication engine 304 may function to send requests, transmitand, receive communications, and/or otherwise provide communication withone or a plurality of systems. In some embodiments, the communicationengine 304 functions to encrypt and decrypt communications. Thecommunication engine 304 may function to send requests to and receivedata from a system through a network or a portion of a network.Depending upon implementation-specific or other considerations, thecommunication engine 304 may send requests and receive data through aconnection, all or a portion of which may be a wireless connection. Thecommunication engine 304 may request and receive messages, and/or othercommunications from associated systems.

The second replication system datastore 306 may function to store, atleast temporarily, data received from one or more other systems. Forexample, the second replication system datastore 306 may store messagesreceived by the communication engine 304, data objects 108, and dataobjects 110. Like other datastores described herein, the secondreplication system datastore 306 may reside local to the secondreplication system 104, and/or comprise a remote storage system (e.g., acloud storage system).

FIG. 4 depicts a flowchart 400 of an example of a method for adaptivedata replication according to some embodiments. In this and otherflowcharts, the flowchart 400 illustrates by way of example a sequenceof steps. It should be understood the steps may be reorganized forparallel execution, or reordered, as applicable. Moreover, some stepsthat could have been included may have been removed to avoid providingtoo much information for the sake of clarity and some steps that wereincluded could be removed, but may have been included for the sake ofillustrative clarity.

In step 402, a master replication system (e.g., first replication system102-1) creates a data object (e.g., data object 108-1). For example, thedata object may comprise one or more points of interest associated witha geographic map stored by the same or different data object (e.g., dataobject 110) that may be shared with one or more remote systems (e.g.,client replication systems 102). In some embodiments, a masterreplication engine creates the data object (e.g., master replicationengine 206).

In step 404, the master replication system stores the data object. Insome embodiments, the master replication stores the data object in adatastore (e.g., first replication system datastore 214).

In step 406, a master replication system shares the data object with oneor more client replication systems (e.g., client replication system102). For example, the client replication systems may obtain a copy ofthe data object (e.g., data object 108-1) from the master replicationsystem over a communication network (e.g., communication network 106).If the client replication system wishes to modify the data object (e.g.,add and/or remove points of interest), the client replication system mayprovide a modification request to the master replication system, and themaster replication system can either approve the request and perform themodification, or deny the request. If the request is approved, themodification may be reflected in the copy of the data object.Alternatively, the copy of the data object may be modified, at leasttemporarily, upon providing the request, and the modification may beconfirmed when the request is approved, or rolled back if the request isdenied. In some embodiments, a client replication engine (e.g., clientreplication engine 206) obtains the copy of the data object, and/or themaster replication engine shares the data object.

In step 408, the client replication system detects one or more networkperformance characteristics of the communication network. In someembodiments, a network performance detection engine (e.g., networkperformance detection engine 202) detects the one or more networkperformance characteristics.

In step 410, the client replication system determines a priority statusof the update request based on the one or more network performancecharacteristics (e.g., if the one or more network performancecharacteristics indicate a strong network connection). In someembodiments, a replication prioritization engine (e.g., replicationprioritization engine 204) determines the priority status.

In step 412, the client replication system triggers a first replicationmode (e.g. a single-master replication mode) based on the prioritystatus (e.g., a critical priority status). The first replication modemay facilitate real-time data replication synchronization. In someembodiments, a replication mode selection engine (e.g., replicationengine selection engine 210) triggers the first replication mode.

In step 414, the client replication system triggers a second replicationmode (e.g., a multi-master replication mode) based on the prioritystatus (e.g., a non-critical priority status). The second replicationmode may provide delayed data replication and/or synchronization. Insome embodiments, the replication mode selection engine triggers thesecond replication mode.

FIG. 5 depicts a flowchart 500 of an example of a method for performinga first replication mode (e.g., a single-master replication mode)according to some embodiments.

In step 502, a first replication system (e.g., first replication system102) generates a first update file (or, replication message) based on areceived update associated with a data object (e.g., data object 108).The first update file is configured for single-master replication of theassociated data, and/or configured to facilitate real-timesynchronization of the associated data. For example, the first updatefile may conform to one or more parameters (e.g., data size,transmission protocols, and/or the like) to help ensure propersynchronization. In some embodiments, a client replication engine (e.g.,client replication engine 208) generates the first update file.

In step 504, the first replication system provides the first update fileover a communication network (e.g., communication network 106) to themaster replication system (e.g., master replication system 102) thatowns the data object. In some embodiments, the client replication engineidentifies the owner of the data object and triggers a communicationengine (e.g., communication engine 212) to provide the first update fileto the owner.

In step 506, the master replication system receives the first updatefile over the communication network. In some embodiments, a masterreplication engine (e.g., master replication engine 206) receives thefirst update file from a communication engine (e.g., communicationengine 212). In step 508, the master replication system deconflicts anyconflicts associated with the first update file. In some embodiments,the master replication engine performs some or all of any deconflcition.In step 510, the master replication system updates the data object usingthe first update file. In some embodiments, the master replicationengine updates the data object. In step 512, the master replicationsystem provide a result of the update (e.g., success, failure, conflict,and/or the like) to the first replication system over the communicationnetwork. In some embodiments, the master replication triggers thecommunication to provide the result.

FIG. 6 depicts a flowchart 600 of an example of a method for performinga second replication mode (e.g., a multi-master replication mode)according to some embodiments.

In step 602, a first replication system (e.g., first replication system102) creates a local copy of a data object (e.g., data object 108). Thedata object may comprise the original or master data object (e.g.,stored by a master replication system that owns the data object), or mayitself comprise a copy of the original or master data object. Access tothe data object may be prevented. In some embodiments, a clientreplication engine (e.g., client replication engine 208) creates thelocal copy of the data object.

In step 604, the first replication system receives an update requestassociated with the copy of the data object. The update request maycomprise a batch of modifications obtained over a period of time (e.g.,a predetermined period of time). The first replication system maylocally deconflict any conflicts associated with the batch ofmodifications. In some embodiments, the client replication performs thedeconflcition.

In step 606, the first replication system provides the update request toa second replication system (e.g., a second replication system 104) overa communication network (e.g., a LAN or high-speed WAN). The secondreplication system comprises a multi-master replication system. Thecommunication network may be a subnetwork of the communication network106, or may be a different communication network altogether. Thecommunication network may be different than a communication network usedto provide communication between first replication systems whenperforming single-master replication. The second replication system maybe selected by the first replication system based on networkconnectivity (e.g., one or more network performance characteristics)between the systems.

In step 608, the second replication system obtains one or more seconddata objects (e.g., data objects) 110 and batches the update requestwith the one or more second data objects. The update request and thesecond data objects may be batched with a previously scheduledreplication of the second data objects. In some embodiments, amulti-master replication engine (e.g., multi-master replication engine302) obtains the second data objects and batches the update request thesecond objects.

In step 610, the second replication system generates a second updaterequest based on the first update request. In some embodiments, thesecond update request may include the first update request and thesecond data objects. In some embodiments, the multi-master replicationengine generates the second update request.

In step 612, the second replication system provides the second updaterequest over a communication network (e.g., a high latency communicationnetwork) to a remote second replication system (e.g., a remote secondreplication system 104). The communication network may be a subnetworkof the communication network 106, or may be a different communicationnetwork altogether. The communication network may be different than acommunication network used to provide communication between firstreplication systems when performing single-master replication. Theremote second replication system may be selected by the secondreplication system based on network connectivity (e.g., one or morenetwork performance characteristics) between the systems, and/or basedon a network connective between remote second replication system and themaster replication system.

In step 614, the remote second replication system process the secondupdate request. For example, the remote second replication system mayreceive the second update request, parse the second update request,identify different data objects (e.g., data objects 108 and/or 110),and/or update corresponding data objects owned by the secondreplication. In some embodiments, a remote multi-master replicationengine (e.g., multi-master replication engine 302) of the remote secondreplication system processes the second update request.

In step 616, the remote second replication system generates a thirdupdate request based on the second update request and/or data objects108 associated with the second update request. In some embodiments, theremote multi-master replication engine generates the third updaterequest.

In step 618, the remote second replication system provides the thirdupdate request to the master replication system. In some embodiments,remote multi-master replication engine identifies the master replicationsystem and/or provides the third update request to the masterreplication over a communication network. The communication network maybe a subnetwork of the communication network 106, or may be a differentcommunication network altogether. The communication network may bedifferent than a communication network used to provide communicationbetween first replication systems when performing single-masterreplication.

In step 620, the master replication system receives the third updaterequest. In some embodiments, a communication engine (e.g.,communication engine 212) of the master replication system receives thethird update request over the communication network, and a masterreplication engine (e.g., master replication engine 206 receives thethird update request from the communication engine of the masterreplication system.

In step, 622, the master replication system processes the third updaterequest. For example, the master replication system may deconflictconflicts, modify corresponding data objects, and provides results toclient replication system of a result of the modification and/ordeconflcition. In some embodiments, the master replication engineprocesses the third update request.

FIG. 7 depicts a flowchart 700 of an example of a method of operation ofa first replication system (e.g., first replication system 102) forperforming adaptive data replication according to some embodiments.

In step 702, a first replication system (e.g., first replication system102) storing a first data object (e.g., data object 108), the first dataobject being associated with a corresponding second data object (e.g.,corresponding data object 108) stored by a remote master replicationsystem (e.g., a master replication system 102). In some embodiments, aclient replication engine (e.g., client replication engine 208) storesthe first data object in a datastore (e.g., a first replication systemdatastore 214).

In step 704, the first replication system detects one or more firstnetwork characteristics of a communication network (e.g., communicationnetwork 106) associated with the first replication system. In someembodiments, a network performance engine (e.g., network performanceengine 202) detects the one or more first network characteristics.

In step 706, the first replication system triggers a first replicationmode (e.g., a single-master replication mode) based on the one or morefirst network characteristics (e.g., indicating a strong networkconnection) of the communication network. The first replication modeincludes receiving a first update of the first data object (step 708),generating a first update file in response to receiving the first updateof the first data object (step 710), the first update file indicatingthe first update of the first data object, and providing the firstupdate file to the remote master replication system over thecommunication network (step 712). In some embodiments, a replicationmode selection engine (e.g., replication mode selection engine 210)performs step 706, and the client replication engine performs steps708-712.

In step 714, the first replication system detects one or more secondnetwork performance characteristics of the communication networkassociated with the first replication system. In some embodiments, thenetwork performance engine detects the one or more second networkcharacteristics.

In step 716, the first replication system triggers a second replicationmode (e.g., a multi-master replication mode) based on the one or moresecond network characteristics (e.g., indicating a weak networkconnection). The second replication mode includes receiving a secondupdate of the first data object (step 718), generating a second updatefile (step 720), and providing the second update file to a secondreplication system (step 722). In some embodiments, the replication modeselection engine (e.g., replication mode selection engine 210) performsstep 716, and the client replication engine performs steps 718-722.

Hardware Implementation

FIG. 8 depicts a block diagram of an example of a computer system 800upon which any of the embodiments described herein may be implemented.The computer system 800 includes a bus 802 or other communicationmechanism for communicating information, one or more hardware processors804 coupled with bus 802 for processing information. Hardwareprocessor(s) 804 may be, for example, one or more general purposemicroprocessors.

The computer system 800 also includes a main memory 806, such as arandom access memory (RAM), cache and/or other dynamic storage devices,coupled to bus 802 for storing information and instructions to beexecuted by processor 804. Main memory 806 also may be used for storingtemporary variables or other intermediate information during executionof instructions to be executed by processor 804. Such instructions, whenstored in storage media accessible to processor 804, render computersystem 800 into a special-purpose machine that is customized to performthe operations specified in the instructions.

The computer system 800 further includes a read only memory (ROM) 808 orother static storage device coupled to bus 802 for storing staticinformation and instructions for processor 804. A storage device 810,such as a magnetic disk, optical disk, or USB thumb drive (Flash drive),etc., is provided and coupled to bus 802 for storing information andinstructions.

The computer system 800 may be coupled via bus 802 to a display 812,such as a cathode ray tube (CRT) or LCD display (or touch screen), fordisplaying information to a computer user. An input device 814,including alphanumeric and other keys, is coupled to bus 802 forcommunicating information and command selections to processor 804.Another type of user input device is cursor control 816, such as amouse, a trackball, or cursor direction keys for communicating directioninformation and command selections to processor 804 and for controllingcursor movement on display 812. This input device typically has twodegrees of freedom in two axes, a first axis (e.g., x) and a second axis(e.g., y), that allows the device to specify positions in a plane. Insome embodiments, the same direction information and command selectionsas cursor control may be implemented via receiving touches on a touchscreen without a cursor.

The computing system 800 may include a user interface module toimplement a GUI that may be stored in a mass storage device asexecutable software codes that are executed by the computing device(s).This and other modules may include, by way of example, components, suchas software components, object-oriented software components, classcomponents and task components, processes, functions, attributes,procedures, subroutines, segments of program code, drivers, firmware,microcode, circuitry, data, databases, data structures, tables, arrays,and variables.

In general, the word “module,” as used herein, refers to logic embodiedin hardware or firmware, or to a collection of software instructions,possibly having entry and exit points, written in a programminglanguage, such as, for example, Java, C or C++. A software module may becompiled and linked into an executable program, installed in a dynamiclink library, or may be written in an interpreted programming languagesuch as, for example, BASIC, Perl, or Python. It will be appreciatedthat software modules may be callable from other modules or fromthemselves, and/or may be invoked in response to detected events orinterrupts. Software modules configured for execution on computingdevices may be provided on a computer readable medium, such as a compactdisc, digital video disc, flash drive, magnetic disc, or any othertangible medium, or as a digital download (and may be originally storedin a compressed or installable format that requires installation,decompression or decryption prior to execution). Such software code maybe stored, partially or fully, on a memory device of the executingcomputing device, for execution by the computing device. Softwareinstructions may be embedded in firmware, such as an EPROM. It will befurther appreciated that hardware modules may be comprised of connectedlogic units, such as gates and flip-flops, and/or may be comprised ofprogrammable units, such as programmable gate arrays or processors. Themodules or computing device functionality described herein arepreferably implemented as software modules, but may be represented inhardware or firmware. Generally, the modules described herein refer tological modules that may be combined with other modules or divided intosub-modules despite their physical organization or storage.

The computer system 800 may implement the techniques described hereinusing customized hard-wired logic, one or more ASICs or FPGAs, firmwareand/or program logic which in combination with the computer systemcauses or programs computer system 800 to be a special-purpose machine.According to one embodiment, the techniques herein are performed bycomputer system 800 in response to processor(s) 804 executing one ormore sequences of one or more instructions contained in main memory 806.Such instructions may be read into main memory 806 from another storagemedium, such as storage device 810. Execution of the sequences ofinstructions contained in main memory 806 causes processor(s) 804 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “non-transitory media,” and similar terms, as used hereinrefers to any media that store data and/or instructions that cause amachine to operate in a specific fashion. Such non-transitory media maycomprise non-volatile media and/or volatile media. Non-volatile mediaincludes, for example, optical or magnetic disks, such as storage device810. Volatile media includes dynamic memory, such as main memory 806.Common forms of non-transitory media include, for example, a floppydisk, a flexible disk, hard disk, solid state drive, magnetic tape, orany other magnetic data storage medium, a CD-ROM, any other optical datastorage medium, any physical medium with patterns of holes, a RAM, aPROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip orcartridge, and networked versions of the same.

Non-transitory media is distinct from but may be used in conjunctionwith transmission media. Transmission media participates in transferringinformation between non-transitory media. For example, transmissionmedia includes coaxial cables, copper wire and fiber optics, includingthe wires that comprise bus 802. Transmission media can also take theform of acoustic or light waves, such as those generated duringradio-wave and infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 804 for execution. For example,the instructions may initially be carried on a magnetic disk or solidstate drive of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 800 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 802. Bus 802 carries the data tomain memory 806, from which processor 804 retrieves and executes theinstructions. The instructions received by main memory 806 may retrievesand executes the instructions. The instructions received by main memory806 may optionally be stored on storage device 810 either before orafter execution by processor 804.

The computer system 800 also includes a communication interface 818coupled to bus 802. Communication interface 818 provides a two-way datacommunication coupling to one or more network links that are connectedto one or more local networks. For example, communication interface 818may be an integrated services digital network (ISDN) card, cable modem,satellite modem, or a modem to provide a data communication connectionto a corresponding type of telephone line. As another example,communication interface 818 may be a local area network (LAN) card toprovide a data communication connection to a compatible LAN (or WANcomponent to communicated with a WAN). Wireless links may also beimplemented. In any such implementation, communication interface 818sends and receives electrical, electromagnetic or optical signals thatcarry digital data streams representing various types of information.

A network link typically provides data communication through one or morenetworks to other data devices. For example, a network link may providea connection through local network to a host computer or to dataequipment operated by an Internet Service Provider (ISP). The ISP inturn provides data communication services through the world wide packetdata communication network now commonly referred to as the “Internet”.Local network and Internet both use electrical, electromagnetic oroptical signals that carry digital data streams. The signals through thevarious networks and the signals on network link and throughcommunication interface 818, which carry the digital data to and fromcomputer system 800, are example forms of transmission media.

The computer system 800 can send messages and receive data, includingprogram code, through the network(s), network link and communicationinterface 818. In the Internet example, a server might transmit arequested code for an application program through the Internet, the ISP,the local network and the communication interface 818.

The received code may be executed by processor 804 as it is received,and/or stored in storage device 810, or other non-volatile storage forlater execution.

Engines, Components, and Logic

Certain embodiments are described herein as including logic or a numberof components, engines, or mechanisms. Engines may constitute eithersoftware engines (e.g., code embodied on a machine-readable medium) orhardware engines. A “hardware engine” is a tangible unit capable ofperforming certain operations and may be configured or arranged in acertain physical manner. In various example embodiments, one or morecomputer systems (e.g., a standalone computer system, a client computersystem, or a server computer system) or one or more hardware engines ofa computer system (e.g., a processor or a group of processors) may beconfigured by software (e.g., an application or application portion) asa hardware engine that operates to perform certain operations asdescribed herein.

In some embodiments, a hardware engine may be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware engine may include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware engine may be a special-purpose processor, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC). A hardware engine may also includeprogrammable logic or circuitry that is temporarily configured bysoftware to perform certain operations. For example, a hardware enginemay include software executed by a general-purpose processor or otherprogrammable processor. Once configured by such software, hardwareengines become specific machines (or specific components of a machine)uniquely tailored to perform the configured functions and are no longergeneral-purpose processors. It will be appreciated that the decision toimplement a hardware engine mechanically, in dedicated and permanentlyconfigured circuitry, or in temporarily configured circuitry (e.g.,configured by software) may be driven by cost and time considerations.

Accordingly, the phrase “hardware engine” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein,“hardware-implemented engine” refers to a hardware engine. Consideringembodiments in which hardware engines are temporarily configured (e.g.,programmed), each of the hardware engines need not be configured orinstantiated at any one instance in time. For example, where a hardwareengine comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware engines) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware engine at one instance oftime and to constitute a different hardware engine at a differentinstance of time.

Hardware engines can provide information to, and receive informationfrom, other hardware engines. Accordingly, the described hardwareengines may be regarded as being communicatively coupled. Where multiplehardware engines exist contemporaneously, communications may be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware engines. In embodiments inwhich multiple hardware engines are configured or instantiated atdifferent times, communications between such hardware engines may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware engines have access.For example, one hardware engine may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware engine may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware engines may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented enginesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented engine” refers to ahardware engine implemented using one or more processors.

Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented engines. Moreover, the one or more processors mayalso operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an Application ProgramInterface (API)).

The performance of certain of the operations may be distributed amongthe processors, not only residing within a single machine, but deployedacross a number of machines. In some example embodiments, the processorsor processor-implemented engines may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented engines may be distributed across a number ofgeographic locations.

Language

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Although an overview of the subject matter has been described withreference to specific example embodiments, various modifications andchanges may be made to these embodiments without departing from thebroader scope of embodiments of the present disclosure. Such embodimentsof the subject matter may be referred to herein, individually orcollectively, by the term “invention” merely for convenience and withoutintending to voluntarily limit the scope of this application to anysingle disclosure or concept if more than one is, in fact, disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

It will be appreciated that an “engine,” “system,” “datastore,” and/or“database” may comprise software, hardware, firmware, and/or circuitry.In one example, one or more software programs comprising instructionscapable of being executable by a processor may perform one or more ofthe functions of the engines, datastores, databases, or systemsdescribed herein. In another example, circuitry may perform the same orsimilar functions. Alternative embodiments may comprise more, less, orfunctionally equivalent engines, systems, datastores, or databases, andstill be within the scope of present embodiments. For example, thefunctionality of the various systems, engines, datastores, and/ordatabases may be combined or divided differently.

The datastores described herein may be any suitable structure (e.g., anactive database, a relational database, a self-referential database, atable, a matrix, an array, a flat file, a documented-oriented storagesystem, a non-relational No-SQL system, and the like), and may becloud-based or otherwise.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, engines, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations may be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource may be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of embodiments of thepresent disclosure as represented by the appended claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

Each of the processes, methods, and algorithms described in thepreceding sections may be embodied in, and fully or partially automatedby, code modules executed by one or more computer systems or computerprocessors comprising computer hardware. The processes and algorithmsmay be implemented partially or wholly in application-specificcircuitry.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this disclosure. In addition, certain method or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto can be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically disclosed, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed fromthe disclosed example embodiments. The example systems and componentsdescribed herein may be configured differently than described. Forexample, elements may be added to, removed from, or rearranged comparedto the disclosed example embodiments.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagramsdescribed herein and/or depicted in the attached figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or steps in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those skilled in the art.

It should be emphasized that many variations and modifications may bemade to the above-described embodiments, the elements of which are to beunderstood as being among other acceptable examples. All suchmodifications and variations are intended to be included herein withinthe scope of this disclosure. The foregoing description details certainembodiments of the invention. It will be appreciated, however, that nomatter how detailed the foregoing appears in text, the invention can bepracticed in many ways. As is also stated above, it should be noted thatthe use of particular terminology when describing certain features oraspects of the invention should not be taken to imply that theterminology is being re-defined herein to be restricted to including anyspecific characteristics of the features or aspects of the inventionwith which that terminology is associated. The scope of the inventionshould therefore be construed in accordance with the appended claims andany equivalents thereof.

1. A system, comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe system to perform: storing a first data object, the first dataobject being associated with a corresponding second data object storedby a remote master replication system; receiving a request to update thefirst data object, the update comprising a first portion and a secondportion; detecting one or more network characteristics of acommunication network; determining a first priority associated with thefirst portion of the update and a second priority associated with thesecond portion of the update, the first priority being different fromthe second priority; and triggering a parallel replication mode, whereintriggering the parallel replication mode comprises: triggering asingle-master replication mode for the first portion of the update basedat least in part on at least one of the first priority or the one ormore network characteristics of the communication network, thesingle-master replication mode enabling real-time synchronization of thefirst portion of the update to the first data object with the seconddata object; and triggering, in parallel with the single-masterreplication mode, a multi-master replication mode for the second portionof the update based at least in part on at least one of the secondpriority or the one or more network characteristics of the communicationnetwork, the multi-master replication mode enabling delayedsynchronization of the second portion of the update to the first dataobject with the second data object.
 2. The system of claim 1, whereintriggering the single-master replication mode comprises sending areplication message to the remote master replication system comprising afirst context-based priority identifier indicative of the firstpriority.
 3. The system of claim 2, wherein the first context-basedpriority identifier indicates a first activity associated with the firstportion of the update, and wherein the first activity is associated witha critical priority status.
 4. The system of claim 1, wherein thesingle-master replication mode exhibits lower latency and lower faulttolerance than the multi-master replication mode.
 5. The system of claim1, wherein the instructions, when executed by the one or moreprocessors, further cause the system to perform: triggering themulti-master replication mode for the first portion of the update inparallel with the single-master replication mode for the first portionof the update.
 6. The system of claim 1, wherein the remote masterreplication system owns the second data object and the first data objectis a copy of the second data object, wherein the system is a clientreplication system for the first data object, and wherein triggering thesingle-master replication mode comprises: generating a first update filebased on the first portion of the update; and sending the first updatefile to the remote master replication system.
 7. The system of claim 6,wherein the first update file conforms to one or more parameters toensure successful real-time synchronization of the first portion of theupdate to the first data object with the second data object.
 8. Thesystem of claim 7, wherein the one or more parameters comprises at leastone of data size of transmission protocols.
 9. The system of claim 6,wherein the instructions, when executed by the one or more processors,cause the system to perform: receiving a batch of requestedmodifications to stored data objects over a period of time, the batch ofrequested modifications including the update to the first data object;and locally deconflicting one or more conflicts associated with thebatch of modifications.
 10. The system of claim 9, wherein the requestto update the first data object is a first request, and wherein locallydeconflicting one or more conflicts associated with the batch ofmodifications comprises: determining that the batch of modificationincludes a second request to update the first data object; determiningthat the second request conflicts with the first request; determiningthat the first request was received prior to the second request; andrejecting the second request.
 11. A method, comprising: storing a firstdata object, the first data object being associated with a correspondingsecond data object stored by a remote master replication system;receiving a request to update the first data object, the updatecomprising a first portion and a second portion; detecting one or morenetwork characteristics of a communication network; determining a firstpriority associated with the first portion of the update and a secondpriority associated with the second portion of the update, the firstpriority being different from the second priority; and triggering aparallel replication mode, wherein triggering the parallel replicationmode comprises: triggering a single-master replication mode for thefirst portion of the update based at least in part on at least one ofthe first priority or the one or more network characteristics of thecommunication network, the single-master replication mode enablingreal-time synchronization of the first portion of the update to thefirst data object with the second data object; and triggering, inparallel with the single-master replication mode, a multi-masterreplication mode for the second portion of the update based at least inpart on at least one of the second priority or the one or more networkcharacteristics of the communication network, the multi-masterreplication mode enabling delayed synchronization of the second portionof the update to the first data object with the second data object. 12.The method of claim 11, wherein triggering the single-master replicationmode comprises sending a replication message to the remote masterreplication system comprising a first context-based priority identifierindicative of the first priority.
 13. The method of claim 12, whereinthe first context-based priority identifier indicates a first activityassociated with the first portion of the update, and wherein the firstactivity is associated with a critical priority status.
 14. The methodof claim 11, wherein the single-master replication mode exhibits lowerlatency and lower fault tolerance than the multi-master replicationmode.
 15. The method of claim 11, further comprising: triggering themulti-master replication mode for the first portion of the update inparallel with the single-master replication mode for the first portionof the update.
 16. The method of claim 11, wherein the remote masterreplication system owns the second data object and the first data objectis a copy of the second data object, wherein the system is a clientreplication system for the first data object, and wherein triggering thesingle-master replication mode comprises: generating a first update filebased on the first portion of the update; and sending the first updatefile to the remote master replication system.
 17. The method of claim16, wherein the first update file conforms to one or more parameters toensure successful real-time synchronization of the first portion of theupdate to the first data object with the second data object.
 18. Themethod of claim 17, wherein the one or more parameters comprises atleast one of data size of transmission protocols.
 19. The method ofclaim 16, further comprising: receiving a batch of requestedmodifications to stored data objects over a period of time, the batch ofrequested modifications including the update to the first data object;and locally deconflicting one or more conflicts associated with thebatch of modifications.
 20. The method of claim 19, wherein the requestto update the first data object is a first request, and wherein locallydeconflicting one or more conflicts associated with the batch ofmodifications comprises: determining that the batch of modificationincludes a second request to update the first data object; determiningthat the second request conflicts with the first request; determiningthat the first request was received prior to the second request; andrejecting the second request.